@LoneMeertens, thank you for addressing the issue! I really like the new structure, a great improvement. :-) Also, adding more documentation/explanation provides significant added value.

• I suggest including Refactoring exercise 3 __CrashCourse__#25 and Update Tutorial IDEAS #1374 as well in this PR, which seems more convenient than having too many issues and PRs related to the same models.
• Regarding more detailed documentation and result visualisation, I suggest maintaining consistency with the SimpleHouse tutorial from IBPSA and following a similar approach. This tutorial has been thoroughly reviewed recently and is consequently in good shape.
• Additionally, we can add DetailedHouse10 as a final Example at the same level as SimpleHouse.

@lucasverleyen Thank you for the detailed feedback and suggestions! 😊 I'm glad you like the new structure and the additional documentation.

I’ll take this up and include open-ideas/CrashCourse#25 and Update Tutorial IDEAS #1374 in this PR as suggested—it does make sense to consolidate related issues and PRs.

Regarding the documentation and result visualization, I'll align it with the SimpleHouse tutorial from IBPSA to ensure consistency and maintain the high standard of quality. I'll also add DetailedHouse10 (as DetailedHouse) as a final example, positioned at the same level as SimpleHouse.

Thanks again for the valuable input!

@LoneMeertens perfect! Thanks a lot! In the mean time, I have looked at the unit tests, but currently, I am not able to solve the issues. DetailedHouse5 does work, but the other examples do not and I don't know why... to be continued in the new year ;-)

@jelgerjansen good catch (__Dymola_Commands)! I suggest adding this to the documentation of the testing framework: https://github.com/open-ideas/IDEAS/blob/master/IDEAS/Resources/Scripts/tests/README.md under Developing new tests. Something like: "Make sure that the file name and path in the model annotation under __Dymola_Comands correspond to the name and path to the .mos file in Resources/Scripts/Dymola/... " What do you think?

@jelgerjansen good catch (__Dymola_Commands)! I suggest adding this to the documentation of the testing framework: https://github.com/open-ideas/IDEAS/blob/master/IDEAS/Resources/Scripts/tests/README.md under Developing new tests. Something like: "Make sure that the file name and path in the model annotation under __Dymola_Comands correspond to the name and path to the .mos file in Resources/Scripts/Dymola/... " What do you think?

@lucasverleyen the __Dymola_Commands is not used when running the unit tests, but links the mos file to the model such that the experiment in the mos file is executed when running the "Simulate and plot" command in Dymola. Note that you don't need a __Dymola_Commands to run the unit tests (which is for example why DetailedHouse5 could be run without problems), but is easier if you want to run unit tests mos files of certain models in Dymola. Therefore, I would maybe not add it, as it is no hard requirement.

If you add it, the file in __Dymola_Commands should of course be linked to the correct mos file (but this is rather a general requirement rather than a unit test requirement). I think that BuildingsPy performs a more detailed check of the model when translating compared to Dymola, as the latter did not throw any errors.